repeatable read
英 [rɪˈpiːtəbl riːd]
美 [rɪˈpiːtəbl riːd]
网络 可重读; 可重复读取; 重复读; 可重复的读; 可反复读
双语例句
- The concurrency decreases and data integrity increases when you move the isolation level from uncommitted read ( UR) to repeatable read ( RR).
当隔离级别从未提交读取（UR）移动到可重复读取（RR）过程中，并发性下降，数据集成性提高。 - Known as Repeatable Read in DB2, this is the strongest isolation level.
在DB2中称为RepeatableRead，是最强的隔离级别。 - For instance, if a Repeatable Read ( RR) scanner has read the partition but not committed yet, detach will wait for the RR scanner to complete before it can make the partition invisible.
例如，如果RepeatableRead（RR）扫描程序已经读取了分区但还没有提交，分离会等到RR扫描程序完成操作后，再使分区不可见。 - These next key locks are only obtained when the key INSERT finds that a scanner with a Repeatable Read ( RR) isolation level has a row lock on the next-higher key in the index.
这些nextkey锁只有在keyINSERT发现带有RepeatableRead（RR）隔离级别的扫描器在索引中的next-higher键上有一个行锁时才能获得。 - Supports table and row level locking and4 isolation levels, RR ( repeatable read), RS ( read stability), CS ( default-cursor stability) and UR ( uncommitted read).
支持表级和行级锁以及4个隔离级别：RR（可重复读）、RS（读可靠）、CS（默认&游标可靠）和UR（未提交读）。 - If the transaction isolation mode is Repeatable Read, then the optimizer would base its choice purely on the estimated costs.
如果事务隔离模式是可重复读（RepeatableRead），那么优化器会将其选择完全基于估算成本。 - This can be used if the isolation level RR ( Repeatable Read) is not used by any programs that operate on the same set of tables.
如果对同一组表进行操作的任何程序都没有使用隔离级别RR（可重复读，RepeatableRead），那么就可以使用上述操作。 - Notice that the ANSI isolation levels and DB2 isolation levels have different names, and "repeatable read" has different meanings.
请注意，ANSI隔离级别和DB2隔离级别使用了不同的名称，“可重复的读取”也有着不同的含义。 - In fact, the only row-level locking that remains during INSERT is the next-key locks that are required to protect an INSERT from adding keys to repeatable read scanners.
实际上，在INSERT期间惟一保持的行级锁是next-key锁，这个锁用于使INSERT不会添加键到可重复的读扫描器。 - Using the Repeatable Read isolation level may result in an automatic table lock in some cases.
使用可重复读隔离级别在某些情况下可能会导致自动执行表锁定。 - Let's first consider repeatable read.
我们先考虑可重复读取。 - With the "Repeatable Read" data region fetch requests issued multiple times within the same transaction will always produce the same result yielding better application throughput.
在相同事务下对“可重复读取”区域内数据的多次请求的结果是相同的，但能够带来更好的应用吞吐量。 - This is an important issue, but using repeatable read isn't the only way to resolve it.
这是一个非常重要的问题，但是使用可重复读取并不是解决问题的唯一途径。 - This leaves you a choice between read committed and repeatable read.
剩下的也就是在“授权读取”和“可重复读取”之间选择了。 - Read committed, Read uncommitted, Repeatable Read, Serializable
提交读，未提交读，可重复读，可串行读